…odule

### What problem does this PR solve?

Issue Number: N/A

Problem Summary: Code review of fe/fe-filesystem/ identified 2 critical bugs,
5 major issues, and 5 minor issues. This commit fixes all of them:

**Critical bugs fixed:**
- ObjFileSystem.exists(): called location.withoutScheme() which strips the URI
  scheme, causing S3Uri/AzureUri parsing to throw on every exists() call.
  Fixed to use location.uri() (full URI with scheme).
- S3FileSystem.globListWithLimit(): pagination loop exited prematurely after
  hitting the limit, so nextMatchAfterLimit was only searched in the remaining
  items of the current S3 page. Fixed to continue paginating until the boundary
  key is found.

**Major issues fixed:**
- RemoteObject.modificationTime() renamed to getModificationTime() for JavaBean
  consistency with the other getters (getKey, getSize, getEtag, getRelativePath).
- S3ObjStorage.buildClient(): removed hard requirement for PROP_ENDPOINT;
  when absent the AWS SDK uses region-only routing for native AWS S3 access.
- BrokerInputStream FD leak: added clientInvalidated flag; close() now skips
  the closeReader RPC when the client was already invalidated by a prior RPC
  failure, preventing a double-invalidate and broker-side FD leak.
- DFSFileSystem.list(): replaced eager listStatus(path) (returns full FileStatus[])
  with lazy listStatusIterator(path) backed by HdfsFileIterator; each hasNext()
  and next() call runs inside the HadoopAuthenticator context for Kerberos safety.
- COS/OBS/OSS providers: added explicit _STORAGE_TYPE_ check so VPC/custom-domain
  endpoints are correctly routed without relying on domain-name pattern matching.

**Minor issues fixed:**
- RemoteIterator, SimpleRemoteIterator, FileSystemIOException removed from SPI
  (unused; FileIterator already covers the same purpose).
- RequestBody.content() no longer declares throws IOException (no IO occurs).
- LocalSeekableInputStream.read() and seek() now throw IOException when closed.
- AzureFileSystem.rename() throws IOException instead of UnsupportedOperationException
  for directory renames, matching the FileSystem contract.
- BrokerFileSystemProvider.create(): null check added for BROKER_PORT before
  Integer.parseInt to give a clear error message instead of NPE.

### Release note

Fix ObjFileSystem.exists() always failing due to withoutScheme(); fix S3 glob
pagination losing results after limit; support AWS region-only S3 access without
an explicit endpoint; fix broker reader FD leak on RPC failure; HDFS listing is
now lazy/streaming.

### Check List (For Author)

- Test: Manual compile verification (all 10 fe-filesystem modules BUILD SUCCESS)
- Behavior changed: Yes — S3 clients no longer require PROP_ENDPOINT for native
  AWS S3; ObjFileSystem.exists() now works correctly; HDFS list is lazy
- Does this need documentation: No

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>